Controlling sensors of a device and notifying sensor clients

ABSTRACT

Techniques for disabling a sensor are described. In an example, the techniques include receiving input data indicating a request to disable a sensor of the device. Based on the input data, the sensor is disabled by at least decoupling the sensor from a power source and decoupling the sensor from an input terminal of a processor of the device. The techniques also include sending, to a plurality of clients that are implemented on the device and that are configured to receive sensor data generated by the sensor, notification data indicating that the sensor is disabled. Further, the techniques include outputting, by a user interface of the device, an indication that the sensor is disabled.

CROSS-REFERENCES TO RELATED APPLICATION

This application is a continuation-in-part application of U.S. patent application Ser. No. 16/849,378, filed Apr. 15, 2020, which is hereby incorporated by reference in its entirety for all purposes.

BACKGROUND

A computing device can have various modalities for user interactions. Depending on the modalities, different types of user inputs can be received and processed to support different types of functionalities of the computing device. For example, a smart speaker can include a microphone. The microphone can detect and send natural language utterance of a user to an audio processor of the computing device for control of, for instance, a volume of the smart speaker or other functionalities thereof. In another example, the smart speaker can also include a camera and a display. In a two-way communication session, the camera can generate and send a video of the user to another remote device. Further, the display can present video received from the remote device. The smart speaker and, similarly, other types of computing devices can include buttons to enable and disable the different modalities.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments in accordance with the present disclosure will be described with reference to the drawings, in which:

FIG. 1 illustrates an example of a computing device that includes a button for controlling a sensing state of a sensor of the computing device, according to embodiments of the present disclosure;

FIG. 2 illustrates an example of a computing device that includes a button for controlling sensing states of multiple sensors of the computing device, according to embodiments of the present disclosure;

FIG. 3 illustrates an example of a diagram of a computing device that controls a sensing state of a sensor of the computing device, according to embodiments of the present disclosure;

FIG. 4 illustrates an example of a diagram of a computing device that controls sensing states of multiple sensors of the computing device, according to embodiments of the present disclosure;

FIG. 5 illustrates an example of a mute controller, according to embodiments of the present disclosure;

FIGS. 6A and 6B illustrate an example of components of a mute controller, according to embodiments of the present disclosure;

FIG. 7 illustrates an example of a power control system and a data control system, according to embodiments of the present disclosure;

FIG. 8 illustrates another example of a power control system and a data control system, according to embodiments of the present disclosure;

FIG. 9 illustrates an example of a user interface, according to embodiments of the present disclosure;

FIG. 10 illustrates an example of a flow for controlling one on more sensing states of one or more sensors of a computing device, according to embodiments of the present disclosure;

FIG. 11 illustrates an example of a flow for controlling a sensor based on a mute button signal, according to embodiments of the present disclosure;

FIG. 12 illustrates an example of a flow for controlling a sensor based on a light source voltage feedback signal, according to embodiments of the present disclosure;

FIG. 13 illustrates an example of a flow for controlling a sensor based on a mute setting signal, according to embodiments of the present disclosure;

FIG. 14 illustrates an example of a computing device that includes multiple clients and a mute control system, according to embodiments of the present disclosure;

FIG. 15 illustrates an example of a diagram of a computing device that includes multiple clients and a mute control system, according to embodiments of the present disclosure;

FIG. 16 illustrates an example of notifying multiple clients included in a computing device about a disabling of a sensor, according to embodiments of the present disclosure;

FIG. 17 illustrates another example of notifying multiple clients included in a computing device about a disabling of a sensor, according to embodiments of the present disclosure;

FIG. 18 illustrates an example of a flow for notifying multiple clients included in a computing device about a disabling of a sensor, according to embodiments of the present disclosure; and

FIG. 19 illustrates an example of an architecture of a computing device that includes a mute control circuitry, according to embodiments of the present disclosure.

DETAILED DESCRIPTION

In the following description, various embodiments will be described. For purposes of explanation, specific configurations and details are set forth in order to provide a thorough understanding of the embodiments. However, it will also be apparent to one skilled in the art that the embodiments may be practiced without the specific details. Furthermore, well-known features may be omitted or simplified in order not to obscure the embodiment being described.

Embodiments of the present disclosure are directed to, among other things, controlling one or more sensing states of one or more sensors of a computing device based on a decoupling of each sensor from a power source and from a data line to a processor of the computing device. In an example, the decoupling is performed by a controller of the computing device, where the controller is separate from and independent of the processor to achieve a higher fidelity and more security in the controlling of the one or more sensing state(s). In particular, the computing device further includes a button operable to request a stop to the one or more sensing states (e.g., each sensor would stop sensing the applicable data), where this request is received by the controller as a request signal. Generally, in the sensing state, the sensor is enabled and is capable of sensing and generating sensed data. When the sensing state is stopped, the sensor is in a mute state. In the mute state, the sensor is disabled and no longer capable of sensing and/or generating sensed data. As described herein below, different techniques are possible to disable the sensor. For example, the sensor can be disabled by decoupling the sensor from the power source and/or decoupling the sensor from the processor. The computing device also includes a user interface that indicates the one or more sensing states and a set of switches that are controllable by the controller. Upon a signal from the controller in response to the request signal from the button, the user interface presents a notification about the mute state. Upon one or more signals from the controller also in response to the request signal from the button, the set of switches opens a power line between the power source and each sensor, thereby powering off the one or more sensors. Additionally or alternatively, the set of switches outputs one or more override signals on one or more data lines between the one or more sensors and the processor, thereby blanking any input data of the one or more sensors to the processor. Depending on latency requirements to terminate execution of computer-readable instructions on the processor, the controller can send a notification signal to the processor about the request, delay the one or more signals to the set of switches by a time delay that is long enough to meet the latency requirement, and send a second notification signal to the processor upon the actual stop to the one or more sensing states. In addition, the controller can receive a voltage level signal from the user interface. Upon detecting a failure at the user interface based on the voltage level signal, the controller can send the one or more signals to the set of switches and the notification signals to the processor, even when the request signal has not been received from the button.

To illustrate, consider an example of a smart speaker that includes a microphone and a mute button operable to mute and unmute the microphone. In this example, the smart speaker also includes a mute controller, a power switch, a data switch, a light source, and system on a chip (SoC). The light source indicates whether the microphone is muted or not. The SoC provides various audio processing functionalities. Upon an activation (e.g., a push) of the mute button, the mute controller detects the activation and determines that the microphone is currently in the sensing state and is to enter a mute state. Accordingly, the mute controller controls the power switch to sever a connection between a power source and the microphone (e.g., by creating an open circuit, such as by causing an open in a power line between the power source and the microphone), thereby powering off the microphone. The mute controller also controls the data switch to zero any audio serial data that is otherwise input to the SoC. The mute controller also controls the light source to emit light indicating that the microphone has been muted.

In this example, the smart speaker further includes a camera, a second power switch coupled to the camera, and a second data switch coupled to the camera. The mute button is also operable to disable and enable the camera. Here also, based on determining that the operational state is the sensing state and should be changed to the mute state, the mute controller controls the second power switch to sever a connection between the power source and the camera, thereby powering off the camera. The mute controller also controls the second data switch to output a camera disabled status to the SoC. Because a graceful shutdown of program code of the camera cannot be immediate and can necessitate a certain length of time (e.g., five-hundred milliseconds), the mute controller delays the controls of the second power switch and the second data switch by a longer time interval (e.g., one second), sends a notification to the SoC about the mute request to trigger the graceful shutdown, and sends a second notification to the SoC about the actual shutdown of the camera at the end of the time interval.

Furthermore, the mute controller receives a voltage level at the light source (e.g., at a cathode of an light emitting diode (LED) of the light source). When the mute button is not activated and the SoC indicates that the smart speaker is in the sensing state, the mute controller continuously compares the voltage level to a voltage threshold (e.g., the voltage threshold set to a minimum voltage value at which light emitted by the LED is visible to a human eye). Based on this comparison, the mute controller determines whether a failure in the light source exists (e.g., when the voltage level exceeds the voltage threshold, corresponding to light being emitted by the LED when this light emission should not be occurring). If the failure is detected, the mute controller controls the above power switches and data switches to power off the microphone and the camera and blank any audio data and video data such that each of the microphone and camera enters the mute state.

Embodiments of the present disclosure provide technological advantages over existing systems to control the sensing states of sensors. In particular, by using a controller and set of switches that are separate from a processor, security of the computing device can be improved. In particular, the processor is prevented from having controls over the stopping and resuming of the sensing states. Hence, even when the processor is compromised (e.g., its software being hacked or includes a bug), the compromise does not affect the stopping and resuming of the sensing states. The fidelity of the stopping and resuming of the sensing states can also be improved by implementing a controller that outputs multiple redundant signals and delays such signals to allow a graceful shutdown of relevant program code executing on the processor In addition, the controller can have a universal design and, hence, can be implemented in different types of devices to support a wide range of sensors. The support can be extended to a sensor of a particular type by indirectly coupling the sensor with the controller via set of switches. These and other technological improvements are further described in connection with the next figures.

In the interest of clarity of explanation, various embodiments of the present disclosure are described in connection with a computing device that includes a microphone and/or a camera. However, the embodiments are not limited as such and apply to controlling the sensing state (e.g., stopping and resuming the sensing state) of any type of sensors including, for instance, motion sensors, temperature sensors, Lidar sensors, and the like. Various embodiments of the present disclosure are also described in connection with an SoC of the computing device. However, the embodiments are not limited as such and apply to any type of processor of the computing device where the processor is coupled with the mute controller and one or more of the sensors controlled by the mute controller. In addition to an SoC, the processor can be any of a central processing unit (CPU), a microcontroller, a field programmable gate array (FPGA), or other type of a processing device.

FIG. 1 illustrates an example of a computing device 100 that includes a button for controlling a sensing state of a sensor of the computing device, according to embodiments of the present disclosure. In this illustrative example, the sensor is a microphone 110 (although other types of the sensor are equivalently possible) and the button is a mute button to mute the microphone 110. The muting includes powering off the microphone 110 and blanking any audio data that would have otherwise been output by the microphone 110.

The computing device 100 also includes a SoC 120 and a power source 130, among other components. The SoC 120 can be an integrated circuit, such as a microchip, that integrates various computing components that provide some or all the functionalities of the computing device 110. These components can include a central processing unit (CPU), a memory and other data storages, analog to digital converters (ADCs), digital to analog converters (DCAs) network interface cards, and input/output ports. This and other potential hardware circuitry and/or software executed on such hardware circuitry provide the functionalities. For instance, the computing device 100 can be a smart speaker. In this case, the functionalities include wakeword detection, audio processing, communications with a backend server over a local area network, transmission and receipt of audio data, playing audio, and the like.

The SoC 120 and the microphone 110 can be coupled over a data line. The data line can carry audio data (digital or analog) from the microphone 110 to the SoC 120 for further processing (e.g., to detect a wakeword, to transmit the audio data in a communications session with a remote computing device, and the like). For instance, the data line can be an I2S bus carrying I2S serial data, where the specification of the I2S bus is defined in the “I2S bus specification,” Philips Semiconductors, Jun. 5, 1996, the content of which is incorporated by reference herein in its entirety.

The power source 130 provides power to various components of the computing device 100. The power can be direct current (DC) power and the power source 130 and/or other components of the computing device 100 can include voltage converters, step-up transformers, step-down transformers, and the like to supply the proper powers to the components of the computing device 100. The power can be supplied over different power lines, such as voltage rails, including a power line between the power source 130 and the microphone 110, and a power line between the power source 130 and the SoC 120. For instance, the power line to the microphone 110 delivers 3.3 volts DC (VDC). A same or a different voltage can be delivered to the SoC 120. The power source 130 can include rechargeable or disposable batteries and/or a receptacle to receive power from an external source, such as from a power outlet.

The microphone 110 can have an operational state that varies between a sensing state and a mute state. The toggle between the states can be initiated via the mute button and controlled via a mute controller coupled with a set of switches configured as gating peripherals, as further illustrated in the next figures. In the sensing state, the microphone 110 detects audio, including natural language utterances, white noise, background noise such as music, and the like, generates audio data based on the detection, and sends the audio data to the SoC 120. In the mute state, the microphone 110 is not to detect any audio and no audio data is to be sent to the SoC 120. Embodiments of the present disclosure prevent the audio detection and audio data transmission by powering off the microphone 110 and/or blanking the output of the microphone 110 to the SoC 120. Blanking includes zeroing the audio data (e.g., setting all data bits to have a zero value in case of digital audio data (e.g., all data bits become “0” bits), setting the voltage level to zero volts of audio data in case of analog audio data).

As illustrated in FIG. 1, prior to activation of the mute button (shown as a button activation 150), the microphone 110 is in the sensing state. In an example, the mute button is a physical button that can be activated in one or more ways. For instance, the physical button is any of a push button, a toggle button, a slide button, or a pull button and its activation can be a push, a slide, a toggle, or a pull, respectively. The mute button can also be a non-reprogrammable button displayed on a GUI, such as a button implemented with non-reprogrammable firmware stored in a read-only memory. In this case, the the SoC 120 cannot reprogram the button (e.g., the firmware), and the activation can be via a click, a touch, or a swipe. Upon deactivation, the microphone 110 is in the sensing state. In the sensing state, the microphone 110 is coupled with the power source 130 over the power line and, thus, is powered on as illustrated with the solid line between the microphone 110 and the power source 130. Also in the sensing state, the microphone 110 is coupled with the SoC 120 over the data line and, thus, outputs audio data to the SoC 120, as illustrated with the solid line between the microphone 110 and the SoC 120.

Upon the button activation 150, the microphone 110 is in the mute state. In the mute state, the microphone 110 is decoupled from the power source 130 as illustrated with the dotted line between the microphone 110 and the power source 130 (e.g., an open is created in the power line). Also in the mute state, the output of the microphone 110 to the SoC 120 is blanked, as illustrated with the dotted line between the microphone 110 and the SoC 120.

To unmute the microphone 110 (e.g., exit the mute state and re-enter the sensing state), the mute button can be selected again (e.g., deactivated). In a further example, the transition from the sensing state to the mute state based on the button activation 150 and/or the transition from the mute state to the sensing state based on the mute button deactivation can be controlled by the mute controller to prevent any controls by the SoC 120 over the transitions. For instance, the SoC 120 (or a program code being executed thereon) is prevented from transitioning the microphone 110 out of the mute state 110 once the button selection 150 occurs. In this way, any compromise to software of the SoC 120 cannot affect this transition.

To indicate the mute state, the computing device 100 includes a light source, as further shown in the next figures. The light source includes, among other components, light elements such as LEDs. Upon the button selection 150, the light elements are controlled (e.g., by the mute controller, as further described in connection with the next figures) to emit light as a visual indicator of the mute state. The light elements can be disposed within, around, and/or in vicinity of the mute button, can be located at a particular location in the computing device 100 (e.g., at a top surface), and/or can be distributed along one or more surfaces (e.g., as an external ring around the top surface). The light source is an example of a user interface that indicates the mute state. Of course, other types of user interfaces are possible including, for instance, an audio interface (e.g., a speaker that plays a particular chime to indicate the mute state) and/or a graphical user interface (GUI) that displays a notification to indicate the mute state. In the sensing state, the light elements may not emit light (and, similarly, other types of user interfaces may not present the indication about the mute state).

FIG. 2 illustrates an example of a computing device 200 that includes a button for controlling sensing states of multiple sensors of the computing device 200, according to embodiments of the present disclosure. In this illustrative example, the sensors include two sensors, although other types of the sensors are equivalently possible. A first sensor is a microphone 210. The second sensor is a camera 215 (e.g., a set of CMOS sensors and relevant circuitry). The button is a mute button to mute both the microphone 210 and the camera 215 upon one selection of the button. The muting includes powering off the microphone 210 and the camera 215 and blanking any audio data and video data that would have otherwise been output by the microphone 210 and the camera 215. The microphone 210 and the camera 215 can support, for instance, an audio and video communication session with a remote device, where audio data and video data can be transmitted to the remote device and where audio data and video data can be received from the remote device and presented at the computing device 200 (e.g., via a speaker and a display of the computing device 200).

The computing device 200 also includes a SoC 220 and a power source 240, among other components. The SoC 220 can be an integrated circuit, such as a microchip, that integrates various computing components that provide some or all the functionalities of the computing device 210, including the audio data and video data processing, transmission, reception, and presentation.

The SoC 220 and the microphone 210 can be coupled over a first data line. The first data line can carry audio data (digital or analog) from the microphone 210 to the SoC 220 for further processing (e.g., to detect a wakeword, to transmit audio data in a communications session with a remote computing device, and the like). For instance, the first data line can be an I2S bus carrying I2S serial data. The SoC 220 and the camera 215 can also be coupled over a second data line. The second data line can carry video data (digital or analog) from the camera 215 to the SoC 220 for further processing (e.g., to detect an object presence in the video data, to transmit the video data in a communications session with the remote computing device, and the like). For instance, the second data line can be a video interconnect bus that supports different compression formats including MPEG-4.

The power source 230 provides power to various components of the computing device 200. The power can be DC power and the power source 240 and/or other components of the computing device 200 can include voltage converters, step-up transformers, step-down transformers, and the like to supply the proper powers to the components of the computing device 200. The power can be supplied over different power lines, such as voltage rails, including a first power line between the power source 240 and the microphone 210, a second power line between the power source 240 and the camera 215, and a power line between the power source 240 and the SoC 220. For instance, the first power line to the microphone 210 delivers 3.3 VDC. The second power line to the camera 215 delivers 5 VDC. The power source 240 can include rechargeable or disposable batteries and/or a receptacle to receive power from an external source, such as from a power outlet.

The microphone 210 can have an operational state that varies between a sensing state and a mute state. In the sensing state, the microphone 210 detects audio, including natural language utterances, white noise, background noise such as music, and the like, generates audio data based on the detection, and sends the audio data to the SoC 220. In the mute state, the microphone 210 is not to detect any audio and no audio data is to be sent to the SoC 220. Similarly, the camera 215 can have an operational state that varies between a sensing state and a mute state. In the sensing state, the camera 215 detects video and sends the resulting video data to the SoC 220. In the mute state, the camera 215 is not to detect any video and no video data is to be sent to the SoC 220.

In an example, the operational states of the microphone 210 and the camera 215 can be synchronized. In other words, while the microphone 210 is in the sensing state, the camera 215 is also in the sensing state, and vice versa. While the microphone 210 is in the mute state, the camera 215 is also in the mute state, and vice versa. This synchronization can be implemented by using a single mute button to toggle between the states. In particular, upon an activation of the mute button (e.g., illustrated in FIG. 2 as a button activation 250), the microphone 210 and the camera 215 transition to the respective mute states. Upon deactivation of the mute button, the microphone 210 and the camera 215 transition to the respective sensing states. The synchronization of the operational states of the microphone 210 and the camera 215 can be referred to herein by a sensing state and a mute state of the computing device 200. In particular, in the sensing state of the computing device 200, the microphone 210 is in its sensing state and the camera 215 is in its sensing state. In the mute state of the computing device, the microphone 210 is in its mute state and the camera 215 is in its mute state.

The mute button can be implemented similarly to the button described in connection with FIG. 1, where this button can be a physical button or a non-reprogrammable button and can be activated for the mute state and deactivated for the sensing state. The toggle between the sensing state and the mute state of the computing device 200 can be initiated via the mute button and controlled via a mute controller coupled with sets of switches configured as gating peripherals, as further illustrated in the next figures.

While the microphone 210 is in the mute state, embodiments of the present disclosure prevent the audio detection and audio data transmission by powering off the microphone 210 and blanking the output of the microphone 210 to the SoC 220. Blanking includes zeroing the audio data (e.g., setting all data bits to have a zero value in case of digital audio data, setting the voltage level to zero volts of audio data in case of analog audio data). Similarly, while the camera 215 is in the mute state, the embodiments of the present disclosure prevent the video detection and video data transmission by powering off the camera 215 and blanking the output of the camera 215 to the SoC 220. This blanking includes, for instance, sending a camera disable signal (e.g., a camera disabled status) to the SoC 220 to disable the video processing at the SoC 220. Alternatively or additionally, blanking the output of the camera 215 includes zeroing the video data on each data line between the camera 215 and the SoC 220.

As illustrated in FIG. 2, prior to the button activation 250, the computing device 200 is in the sensing state, whereby the microphone 210 is in its sensing state and the camera 215 is in its sensing state. In its sensing state, the microphone 210 is coupled with the power source 240 over the first power line and, thus, is powered on as illustrated with the solid line between the microphone 210 and the power source 240. Also in its sensing state, the microphone 210 is coupled with the SoC 220 over the first data line and, thus, outputs audio data to the SoC 220, as illustrated with the solid line between the microphone 210 and the SoC 220. Similarly, in its sensing state, the camera 215 is coupled with the power source 240 over the second power line and, thus, is powered on as illustrated with the solid line between the camera 215 and the power source 240. Also in its sensing state, the camera 215 is coupled with the SoC 220 over the second data line and, thus, outputs video data to the SoC 220, as illustrated with the solid line between the camera 215 the SoC 220.

Upon the button activation 250, the computing device 200 is in the mute state, whereby the microphone 210 is in its mute state and the camera 215 is in its mute state. In its mute state, the microphone 210 is decoupled from the power source 240 as illustrated with the dotted line between the microphone 210 and the power source 240 (e.g., an open is created in the first power line). Also in its mute state, the output of the microphone 210 to the SoC 220 is blanked, as illustrated with the dotted line between the microphone 210 and the SoC 220. Similarly, in its mute state, the camera 215 is decoupled from the power source 240 as illustrated with the dotted line between the camera 215 and the power source 240 (e.g., an open is created in the second power line). Also in its mute state, the output of the camera 215 to the SoC 220 is blanked, as illustrated with the dotted line between the camera 215 and the SoC 220.

To unmute the computing device 200 (e.g., exit its mute state and re-enter its sensing state), the mute button can be selected again. In an example, the transition from the sensing state to the mute state based on the button activation 250 and/or the transition from the mute state to the sensing state based on the mute button deactivation can be controlled by the mute controller to prevent any controls by the SoC 220 over the transitions. For instance, the SoC 220 (or a program code being executed thereon) is prevented from transitioning any of the microphone 210 or the camera 215 out of the respective mute state once the button activation 250 occurs. In this way, any compromise to software of the SoC 220 cannot affect this transition.

To indicate the mute state, the computing device 200 includes a light source, as further shown in the next figures. The light source includes, among other components, light elements such as LEDs. Upon the button activation 250, the light elements are controlled (e.g., by the mute controller, as further described in connection with the next figures) to emit light as a visual indicator of the computing device's 200 mute state. The light elements can be disposed within, around, and/or in vicinity of the mute button, can be located at a particular location in the computing device 200 (e.g., at a top surface), and/or can be distributed along one or more surfaces (e.g., as an external ring around the top surface). The light source is an example of a user interface that indicates the computing device's 200 mute state. Of course, other types of user interfaces are possible including, for instance, an audio interface (e.g., a speaker that plays a particular set of chimes to indicate the computing device's 200 mute state) and/or a graphical user interface (GUI) that displays a set of notifications to indicate the computing device's 200 mute state. In the computing device's 200 sensing state, the light elements may not emit light (and, similarly, other types of user interfaces may not present the set of indications about the mute states).

Although FIG. 2 illustrates the computing device 200 as including a single SoC 220 and a single power source 240, other configurations of the computing device 200 are possible. For instance, the computing device 200 can include more than one SoC, each coupled to one of the microphone 210 or the camera 215, and/or more than one power source, each coupled to one of the microphone 210 or the camera 215.

Furthermore, although FIG. 1 illustrates a computing device that includes a single sensor, and although FIG. 2 illustrates a computing device that includes two sensors, a larger number of sensors (e.g., more than two) is possible to include in a computing device. Nonetheless, and as further illustrated in the next figures, a single mute controller may suffice to support any number of sensors. This mute controller can be thought of as a universal controller capable of supporting one or more sensors and one or more different types of sensors. To account for the variability in the number and/or type of sensors, one or more, as applicable, gating peripherals included in the computing device, where the gating peripheral(s) is (are) coupled with the mute controller, the sensor(s), and the SoC.

In an example, the button included any of the computing device 100 or the computing device 200 is implemented as a push and hold button. Upon a push and hold of the button for a time duration smaller than a predefined time length (e.g., three seconds or some other time value), the relevant sensor(s) (e.g., any of the microphones 110 or 210 and, as applicable, the camera 215) is disabled. Upon a push and hold of the button for a time duration larger than the predefined time length, the relevant sensor(s) are not automatically muted. Instead, for instance, a user notification is presented (e.g., via a speaker or a GUI) to confirm that the mute state should be entered.

FIG. 3 illustrates an example of a diagram of a computing device 300 that controls a sensing state of a sensor of the computing device 300, according to embodiments of the present disclosure. In this illustrative example, the sensor is a microphone 320 (although other types of the sensor are equivalently possible) and the computing device 300 is an example of the computing device 100 of FIG. 1.

As illustrated, the computing device 300 includes a button 310, the microphone 320, a light source 330, a SoC 340, a mute controller 350, a switch set 360, and a power source 380. The button 310 can be a mute button operable to mute the microphone 320. The button 310 is coupled with the mute controller 350 over a data line that carries a mute button signal from the button 310 to the mute controller 350. Other components can be coupled on this data line including, for instance, a resistor and capacitor (R/C) circuit connected in between the button 310 and the mute controller 350, where this R/C circuit filters out edges of the mute button signal. The button 310 can be implemented as a switch. When the switch is open, the mute button signal is set to inactive to indicate that the computing device 300 (or, equivalently, the microphone 320) should be in the sensing state. When the switch is closed, the mute button signal is set to active to indicate that the computing device 300 (or, equivalently, the microphone 320) a request to stop the sensing state and be in the mute state instead. Inactive and active can be set by using a low voltage “L” (e.g., 0 VDC) for inactive and a high voltage “H” (e.g., 5 VDC) for active, or vice versa depending on the implementation.

In addition to receiving the mute button as a first input signal, the mute controller 350 can receive additional input signals. For instance, the mute controller 350 is coupled with the SoC 340 over a data line and with the light source 330 over another data line. From the SoC 340, the mute controller 350 receives a mute setting signal and a light source intensity signal. The mute setting signal indicates whether the SoC 340 is operating under the assumption that the microphone 320 is in the sensing state (e.g., mute setting signal set to inactive) or is in the mute state (e.g., mute setting signal set to active). The light source intensity signal indicates a setting according to which the light source 330 should emit light to indicate the mute state (e.g., the setting can be a power setting for the light emission).

From the light source 330, the mute controller 350 receives a light source voltage feedback signal indicating a voltage level at the light source 330 (e.g., at a cathode of an LED of the light source 330). As further described in the next figures, the mute controller 350 can determine a failure in the light source 330 based on the voltage level (e.g., a hardware failure causing the light source to emit visible light when no such light emission should be occurring) and can force, as applicable, the transition from the sensing state to the mute state.

Based on the received input signals, the mute controller 350 can generate and output multiple output signals. For redundancy and higher fidelity, some of the output signals can be redundant. In addition, for a graceful termination of relevant software execution on the SoC 340, some of the output signals can be delayed relative to other output signals. In an example, the mute controller 350 is dedicated hardware that implements logic to generate the output signals based on the input signals, where this dedicated hardware can include transistors, diodes, and other electronic components representing logic gates as further described in connection with FIG. 6. In another example, the mute controller 350 can be implemented as a field-programmable gate array (FPGA), a microprocessor, a central processing unit (CPU), an SoC, and/or other circuitry that may execute firmware and/or software, where such circuitry is non-programmable, to prevent any compromise in the SoC 340 from impacting the controls of the mute controller 350.

In an example, the mute controller 350 is coupled with the light source 330, the SoC 340, and the switch set 360 over data lines that carry the output signals. To the light source 330, the mute controller 350 sends a light source on/off signal and a light source intensity signal. One value of the light source on/off signal indicates that the light source should emit visible light (e.g., the light source on/off signal is set to active”). Another value of the light source on/off signal indicates that the light source should not emit visible light (e.g., the light source on/off signal is set to inactive). When visible light should be emitted, the light source intensity signal indicates a setting for the light emission (e.g., the power level of the light emission), where this setting can correspond to the setting indicated by the SoC 340 in one of the input signals to the mute controller 350.

To the SoC 340, the mute controller 350 outputs a button selection signal and, optionally, a mute status signal. One value of the button selection signal indicates that the button 310 was selected (e.g., indicates an activation of the button 310). For instance, the button selection signal is set to inactive to indicate the mute state). Another value of the button selection signal that the button 310 was deselected (e.g., indicates a deactivation of the button 310). For instance, the button selection signal is set to active to indicate the sensing state). The mute status signal can indicate the operational status of the microphone 320 (e.g., whether in the mute state or the sensing state). For instance, the mute status signal is set to active to indicate the sensing state and set to inactive to indicate the mute state. When the two signals are used, the mute controller 350 transmits the mute status signal to the SoC 340 following a delay time interval relative to the transmission of the button selection signal, where the delay time interval is large enough to enable the SoC 340 to gracefully terminate the execution of any microphone-related program code. In other words, when the two signals are used, the button selection signal indicates that the button 310 has been selected and the microphone 320 is about to enter at the end of the delay time interval, and the mute status signal indicates to the SoC 340 that the microphone 320 is now actually in the mute state.

To the switch set 360, the mute controller 350 outputs a first mute state signal and, optionally, a second mute state signal. The second mute state signal can be redundant to the first mute state signal. For instance, the second mute state signal is an invert of the first mute state signal. By using an invert, logic (e.g., implemented as logic gates) can be included in the switch set 360 to help against controls of the SoC 340 over the controls of the mute controller 350 and/or operations of the switch set 360, as further described in the next figures. In addition, the first mute state signal (and, similarly, the second mute state signal) can be delayed by the delay time interval relative to the button selection signal transmitted to the SoC 340. One value of the first mute state signal indicates the operational status of the microphone 320 (e.g., the first mute state signal is set to inactive to indicate the sensing state). Another value of the first mute state signal indicates a change to the operational status of the microphone 320 (e.g., the first mute state signal is set to active to indicate the mute state).

Upon receiving the indication from the mute controller 350 that the microphone 320 should be in the mute state (e.g., by receiving the first mute state signal and, optionally, the second mute state signal), the switch set 360 decouples the microphone 320 from the power source 380 and blanks the data line that couples the microphone 320 to the SoC 340. Conversely, upon receiving the indication from the mute controller 350 that the microphone 320 should be in the sensing state (e.g., by receiving the first mute state signal and, optionally, the second mute state signal), the switch set 360 couples the microphone 320 to the power source 380 and no longer blanks the data line that couples the microphone 320 to the SoC 340.

In an example, the switch set 360 includes a power switch system 362 and a data control system 364. The power switch system 362 receives the first mute state signal. When the first mute state signal indicates that the microphone 320 should be in the mute state (e.g., the voltage level of the first mute state signal is active”), the power switch system 362 severs a connection between the power source 380 and the microphone 320, such as by creating an open circuit (e.g., opens a switch) on the power line that couples the power source 380 and the microphone 320, thereby powering off the microphone 320. Conversely, when the first mute state signal indicates that the microphone 320 should be in the sensing state (e.g., the voltage level of the first mute state signal is inactive), the power switch system 362 closes the circuit (e.g., closes the switch) on the power line that couples the power source 380 and the microphone 320, thereby powering on the microphone 320. The power switch system 362 can include any of a power switch or a power regulator.

When only the first mute state signal is transmitted by the mute controller 350, the data control system 364 receives the first mute state signal. When redundancy is used, where the second mute state signal is also transmitted by the mute controller 350, the data control system 364 receives the second mute state signal instead. In both cases, when the mute state is indicated, the data control system 364 zeros the voltage level on the data line. When the sensing state is indicated, no zeroing is performed, thereby the actual audio data sent by the microphone 320 is carried over the data line to the SoC 340. The data control system 364 can include any of a data switch or a set of logic gates.

As illustrated in FIG. 3, the mute controller 350 is implemented and operated separately from the SoC 340 to increase the security of the muting of the microphone 320. Such an implementation can also involve implementing the switch set 360 separately from the SoC 340. The switch set 360 can be implemented in the mute controller 350. However, the switch set 360 can be implemented separately from the mute controller 350, so that the mute controller 350 can be designed as a universal mute controller that can be coupled with multiple switch sets, each corresponding to one or more sensors, as further described in FIG. 4. In this way, each switch set can be implemented as a gating peripheral.

FIG. 4 illustrates an example of a diagram of a computing device 400 that controls sensing states of multiple sensors of the computing device 400, according to embodiments of the present disclosure. In this illustrative example, the sensors include two sensors, although other types of the sensors are equivalently possible. A first sensor is a microphone 420. The second sensor is a camera 425. The computing device 400 is an example of the computing device 200 of FIG. 2. A sensing state of the computing device 400 corresponds to both the microphone 420 and the camera 425 being in a respective sensing state. A mute state of the computing device 400 corresponds to both the microphone 420 and the camera 425 being in a respective mute state.

As illustrated, the computing device 400 includes a button 410, the microphone 420, the camera 425, a light source 430, a SoC 440, a mute controller 450, a switch set 460, a switch set 470, and a power source 480. Each of the button 410, the microphone 420, the light source 430, the SoC 440, the mute controller 450, and the switch set 460 can be the same as the button 310, the microphone 320, the light source 330, the SoC 340, the mute controller 350, and the switch set 360, respectively, of FIG. 3. The switch set 470 is implemented to couple the mute controller 450 to the camera 425, thereby extending the controls of the mute controller 450 to not only cover the microphone 420, but to also cover the camera 425.

In an example, the button 410 is a mute button operable to mute the microphone 420 and the camera 425. The button 410 is coupled with the mute controller 450 over a data line that carries a mute button signal from the button 410 to the mute controller 450. Other components can be coupled on this data line including, for instance, an R/C circuit connected in between the button 410 and the mute controller 450, where this R/C circuit filters out edges of the mute button signal. The button 410 can be implemented as a switch. When the switch is open, the mute button signal is set to inactive to indicate that the computing device 400 (or, equivalently, the microphone 420 and the camera 425) should be in the sensing state. When the switch is closed, the mute button signal is set to active to indicate that the computing device 400 (or, equivalently, the microphone 420 and the camera 425) sent a request to stop the sensing state and be in the mute state instead.

In addition to receiving the mute button as a first input signal, the mute controller 450 can receive additional input signals. For instance, the mute controller 450 is coupled with the SoC 440 over a data line and with the light source 430 over another data line. From the SoC 440, the mute controller 450 receives a mute setting signal and a light source intensity signal. The mute setting signal indicates whether the SoC 440 is operating under the assumption that the computing device 400 is in the sensing state (e.g., mute setting signal set to inactive) or is in the mute state (e.g., mute setting signal set to active). The light source intensity signal indicates a setting according to which the light source 430 should emit light to indicate the mute state (e.g., the setting can be a power setting for the light emission).

From the light source 430, the mute controller 450 receives a light source voltage feedback signal indicating a voltage value at the light source 430 (e.g., at an input or output of the light source, such as at a cathode of an LED of the light source 430). As further described in the next figures, the mute controller 450 can determine a failure in the light source 430 based on the voltage value (e.g., a hardware failure causing the light source to emit visible light when no such light emission should be occurring) and can force, as applicable, the transition from the sensing state to the mute state.

Based on the received input signals, the mute controller 450 can generate and output multiple output signals. For redundancy and higher fidelity, some of the output signals can be redundant. In addition, for a graceful termination of relevant software execution on the SoC 440, some of the output signals can be delayed relative to other output signals. In an example, the mute controller 450 is dedicated hardware that implements logic to generate the output signals based on the input signals, where this dedicated hardware can include transistors, diodes, and other electronic components representing logic gates as further described in connection with FIG. 6. In another example, the mute controller 450 can be implemented as an FPGA, a microprocessor, a CPU, an SoC, and/or other circuitry that may execute firmware and/or software, where such circuitry is non-programmable, to prevent any compromise in the SoC 440 from impacting the controls of the mute controller 450.

In an example, the mute controller 450 is coupled with the light source 430, the SoC 440, the switch set 460, and the switch set 470 over data lines that carry the output signals. To the light source 430, the mute controller 450 sends a light source on/off signal and a light source intensity signal. One value of the light source on/off signal indicates that the light source should emit visible light (e.g., the light source on/off signal is set to active). Another value of the light source on/off signal indicates that the light source should not emit visible light (e.g., the light source on/off signal is set to inactive). When visible light should be emitted, the light source intensity signal indicates a setting for the light emission (e.g., the power level of the light emission), where this setting can correspond to the setting indicated by the SoC 440 in one of the input signals to the mute controller 450.

To the SoC 440, the mute controller 450 outputs a button selection signal and, optionally, a mute status signal. One value of the button selection signal indicates that the button 410 was selected (e.g., indicates an activation of the button 410). For instance, the button selection signal is set to inactive to indicate the mute state). Another value of the button selection signal that the button 410 was deselected (e.g., indicates a deactivation of the button 410. For instance, the button selection signal is set to active to indicate the sensing state. The mute status signal can indicate the operational status of the computing device 400 (e.g., whether in the mute state or the sensing state). For instance, the mute status signal is set to active to indicate the sensing state and set to inactive to indicate the mute state. When the two signals are used, the mute controller 450 transmits the mute status signal to the SoC 440 following a delay time interval relative to the transmission of the button selection signal, where the delay time interval is large enough to enable the SoC 440 to gracefully terminate the execution of any microphone-related program code and/or any camera-related program code. In other words, when the two signals are used, the button selection signal that the button 410 has been selected and the computing device 400 is about to enter at the end of the delay time interval, and the mute status signal indicates to the SoC 440 that the computing device 400 is now actually in the mute state.

To the switch set 460, the mute controller 450 outputs a first mute state signal and, optionally, a second mute state signal. The second mute state signal can be redundant to the first mute state signal. For instance, the second mute state signal is an invert of the first mute state signal. By using an invert, logic (e.g., implemented as logic gates) can be included in the switch set 460 to help against controls of the SoC 440 over the controls of the mute controller 450 and/or operations of the switch set 460, as further described in the next figures. In addition, the first mute state signal (and, similarly, the second mute state signal) can be delayed by the delay time interval relative to the button selection signal transmitted to the SoC 440. One value of the first mute state signal indicates the operational status of the microphone 420 (e.g., the first mute state signal is set to inactive” to indicate the sensing state of the microphone 420). Another value of the first mute state signal indicates a change to the operational status of the microphone 420 (e.g., the first mute state signal is set to active to indicate the mute state of the microphone 420).

Upon receiving the indication from the mute controller 450 that the microphone 420 should be in the mute state (e.g., by receiving the first mute state signal and, optionally, the second mute state signal), the switch set 460 decouples the microphone 420 from the power source 480 and blanks the data line that couples the microphone 420 to the SoC 440. Conversely, upon receiving the indication from the mute controller 450 that the microphone 420 should be in the sensing state (e.g., by receiving the first mute state signal and, optionally, the second mute state signal), the switch set 460 couples the microphone 420 to the power source 480 and no longer blanks the data line that couples the microphone 420 to the SoC 440.

In an example, the switch set 460 includes a power switch system 462 and a data control system 464. The power switch system 462 receives the first mute state signal. When the first mute state signal indicates that the microphone 420 should be in the mute state (e.g., the voltage level of the first mute state signal is active”), the power switch system 462 severs a connection between the power source 480 and the microphone 420, such as by creating an open circuit (e.g., opens a switch) on the power line that couples the power source 480 and the microphone 420, thereby powering off the microphone 420. Conversely, when the first mute state signal indicates that the microphone 420 should be in the sensing state (e.g., the voltage level of the first mute state signal is inactive), the power switch system 462 closes the circuit (e.g., closes the switch) on the power line that couples the power source 480 and the microphone 420, thereby powering on the microphone 420.

When only the first mute state signal is transmitted by the mute controller 450, the data control system 464 receives the first mute state signal. When redundancy is used, where the second mute state signal is also transmitted by the mute controller 450, the data control system 464 receives the second mute state signal instead. In both cases, when the mute state is indicated, the data control 464 zeros the voltage level on the data line. When the sensing state is indicated, no zeroing is performed, thereby the actual audio data sent by the microphone 420 is carried over the data line to the SoC 440. The data control system 464 can include any of a data switch or a set of logic gates.

To the switch set 470, the mute controller 450 also outputs the first mute state signal and, optionally, the second mute state signal. For instance, the one or more data lines that couple the mute controller 450 with the switch set 460 also couple the mute controller with the other switch set 470.

Upon receiving the indication from the mute controller 450 that the microphone 420 should be in the mute state (e.g., by receiving the first mute state signal and, optionally, the second mute state signal), the switch set 470 decouples the camera 425 from the power source 480 and blanks the data line that couples the camera 425 to the SoC 440. Conversely, upon receiving the indication from the mute controller 450 that the camera 425 should be in the sensing state (e.g., by receiving the first mute state signal and, optionally, the second mute state signal), the switch set 470 couples the camera 425 to the power source 480 and no longer blanks the data line that couples the camera 425 to the SoC 440.

In an example, the switch set 470 includes a power switch system 472 and a data switch 474. The power switch system 472 receives the first mute state signal. When the first mute state signal indicates that the camera 425 should be in the mute state (e.g., the voltage level of the first mute state signal is active), the power switch system 472 severs a connection between the power source 480 and the camera 425, such as by creating an open circuit (e.g., opens a switch) on the power line that couples the power source 480 and the camera 425, thereby powering off the camera 425. Conversely, when the first mute state signal indicates that the camera 425 should be in the sensing state (e.g., the voltage level of the first mute state signal is inactive), the power switch system 472 closes the circuit (e.g., closes the switch) on the power line that couples the power source 480 and the camera 425, thereby powering on the camera 425. Each of one of the power switch systems 462 and 472 can include any of a power switch or a power regulator.

When only the first mute state signal is transmitted by the mute controller 450, the data control system 474 receives the first mute state signal. When redundancy is used, where the second mute state signal is also transmitted by the mute controller 450, the data control system 474 receives the second mute state signal instead. In both cases, when the mute state is indicated, the data control switch 474 sets an override signal on the data line between the camera 425 and the SoC 440. Different types of overrides are possible. In one example, the override signal indicates that the camera is disabled (e.g., the override signal is a camera disable signal). In another example, the override signal can zero any video data that would have been otherwise transmitted from the camera 425 to the SoC 440 (in which case, the data line can include multiple data lines, each carrying a subset of the video data). When the sensing state is indicated, no override signal is used, thereby the actual audio data sent by the microphone 420 is carried over the data line to the SoC 440. The data control system 474 can include any of a data switch or a set of logic gates.

As illustrated in FIGS. 3 and 4, the mute controller can be implemented as a universal mute controller. Controls by the universal mute controller can extended to multiple sensors by coupling the universal mute controller to multiple switch sets, each implemented as a gating peripheral and coupled to a corresponding sensor. The first mute state signal and, optionally, the second mute state signal are transmitted from the universal mute controller to each of the switch sets to control operations of these switch sets.

FIG. 5 illustrates an example of a mute controller 500, according to embodiments of the present disclosure. The mute controller 500 receives multiple input signals from a mute button, SoC, and a light source of a computing device and outputs multiple output signals to a switch set, the SoC, and the light source of the computing device. The mute controller is an example of the mute controller 350 of FIG. 3 and the mute controller 450 of FIG. 4.

The input signals include a mute button signal 510 from the button, a mute setting signal 520 and a light source intensity signal 530 from the SoC, and a light source voltage feedback signal 540 from the light source. The mute button signal 510, the mute setting signal 520, the light source intensity signal 530, and the light source voltage feedback signal 540 correspond to the input signals described in connection with FIGS. 3 and 4.

The output signals include a mute state signal (A) 550 and, optionally for redundancy, a mute state signal (B) 560 to the switch set, a button selection signal 570 and, optionally for redundancy and graceful software termination, a mute status signal 580 to the SoC, and a light source on/off signal 590 and a light source intensity signal 595 to the light source. The mute state signal (A) 550, the mute state signal (B) 560, the button selection signal 570, the mute status signal 580, the light source on/off signal 590, and the light source intensity signal 595 correspond to the output signals described in connection with FIGS. 3 and 4.

In an example, the controller 500 implements logic, in hardware and/or software, to generate the output signals based on the input signals. Generally, the logic uses the mute button signal 510 as a control to enter into a mute state and exit from the mute state back into a sensing state. The logic uses also the light source voltage feedback signal 540 to force the mute state upon detection of a failure in the light source. The SoC can also request the mute state via the mute setting signal 520. Once the mute state is entered, the SoC is prevented from changing the operational state back to the sensing state. In other words, the mute setting signal 520 from the SoC is not usable to transition to the sensing state and only the mute button signal 510 or the light source intensity signal 530 (upon detection that the failure no longer exists) are usable for the transition to the sensing state. This logic can be implemented, for instance, as a set of logic gates in hardware and/or in part as a look-up table in software.

In particular, when the mute button signal 510 indicates an activation of a button (e.g., a request to stop the sensing state and enter the mute state), the mute controller 500 also determines whether a sensor is in the mute state or not. For instance, the controller 500 stores an indication (e.g., a flag or a bit) of an operational state of the sensor (e.g., whether in the sensing state or the mute state). If the sensor is already in the mute state, the sensor is already disabled and the controller need not decouple the sensor from a power source and/or the SoC. If the sensor is in the sensing state, the sensor is enabled and the controller 500 updates the indication to store the mute state. The toggling of the operational state to the mute state results in the mute controller 500 setting the various output signals to indicate the mute state.

Similarly, when the light source voltage feedback signal 540 indicates a voltage value at the light source, where the voltage value is large enough to permit the emission of visible light, the mute controller 500 also determines whether the mute setting signal 520 indicates that the SoC is operating under the assumption that the computing device is in the mute state. If not, the mute controller 500 detects a failure at the light source because the light source is emitting visible light indicating that the computing device is in the mute state, whereas the SoC is operating under the assumption of the sensing state. Because the emitted light can be visible to a user, the user experience is accorded a higher priority, and the mute controller 500 forces the mute state. In this case, the mute controller 500 stores the mute state (e.g., by updating the indication of the operational status) and sets the various output signals to indicate the mute state. If the SoC is already operating under the mute state, the mute controller 500 continues to generate the output signals indicating the mute state. When the voltage value indicates normal operations of the light source, the mute controller 500 accords higher priority to the mute button signal 510 and/or the mute setting signal 520.

When the failure of the light source is detected and the mute state is entered without the button being activated, a notification can be provided to the user to indicate the failure. Depending on the type of user interfaces that the computing device supports, the notification can include audio data output on a speaker of the computing device and/or text data output at a GUI of the computing device. Further, the notification can be output automatically upon disabling the sensor. Alternatively, the notification can be output upon receiving the mute button signal 510 indicating a selection of the button (e.g., activation) subsequent to the disabling of the sensor.

In comparison, when the mute setting signal 520 indicates a request for the mute state (e.g., set to active), this request can correspond to an application request from the SoC to mute the computing device (e.g., based on a natural language utterance detected by the computing device and processed as a command to mute the computing device). In this case, the mute controller 500 determines whether operational status is the mute state, the mute button signal 510 already indicates the request, and/or whether the light source voltage feedback signal 540 already forces the mute state. If not, the mute controller 500 sets the various output signals to indicate the mute state. If the mute state is already entered, requested, or forced, the mute controller 500 continues to generate the output signals indicating the mute state.

The mute setting signal 520 is sent from the SoC. In an example, the SoC cannot use the mute setting signal 520 to request the sensing state (e.g. to re-enable the sensor). In this example, only when the mute button signal 510 indicates no request for the mute state and the light source voltage feedback signal 540 indicates no forcing of the mute state does the mute controller 500 unmute the computing device

In an example, the button is implemented as a push and hold button. In this case, upon the mute button signal 510 has been selected (e.g., pushed), the mute controller 500 determines a time duration during which the mute button remains selected (e.g., held). For instance, the mute controller 500 starts a timer upon the mute button signal 510 changing (e.g., from active to inactive, or vice versa depending on the implementation) and stops the time upon the mute button signal 510 changing again (e.g., from inactive to active, or vice versa depending on the implementation). The mute controller 500 compares the measured time duration between the start and the stop to a predefined time length (e.g., three seconds or some other value that may be set in a user setting). If the time duration is shorter than the predefined time length, the mute controller 500 sets the various output signals to indicate the mute state. Otherwise, the mute controller 500 does not send such outputs.

The light source voltage feedback signal 540 is input to the mute controller 500. The setting indicated by this signal 540 for the light source is sent by the controller 500 in the light source intensity signal 595.

In an example, some or all of the input signals and/or output signals are implemented in the digital domain. For instance, each of the mute button signal 510, mute setting signal 520, and light source intensity signal 530 is a digital signal that includes input data to the mute controller 500. In particular, the mute button signal 510 provides button ON data and button OFF data. The button ON data indicates that the button has been selected (e.g. pushed). The button OFF data indicates that the button has been deselected. Each of the selection and deselection can be indicated with a single bit. The light source intensity signal 530 provides light intensity data indicating a light intensity of the light source for light emission from the light source. A single bit can be used, where the light intensity can be controlled between two levels. Alternatively, multiple “N” bits can be used to provide “2^(N)” setting controls.

Further, each of the mute state signal (A) 550, the mute state signal (B) 560, the button selection signal 570, the mute status signal 580, the light source on/off signal 590, and the light source intensity signal 595 is a digital signal that includes output data sent from the mute controller 500 to a switch set, the SoC, or the light source as applicable. The mute state signal (A) 550 provides first output data indicating the mute state or the sensing state. A single bit can be used for this indication. For instance, when the first output data is set to active (e.g., a high voltage level “H” corresponding to a “1” bit), the mute state is indicated. When the first output data is set to inactive (e.g., a low voltage level “L” corresponding to a “0” bit), the sensing state is indicated. The mute state signal (B) 560 provides second output data indicating the mute state or the sensing state. A single bit can be used for this indication. The second output data can be redundancy to the first output data and/or can be an invert of the first output data. For instance, when the first output data is set to active to indicate the mute state, the second output data is set to inactive to also indicate the mute state. When the first output data is set to inactive to indicate the sensing state, the second output data is set to active to also indicate the sensing state. The button selection signal 570 provides third output data indicating the activation or deactivation of the button. A single bit can be used for this indication. For instance, when the third output data is set to inactive, the button activation is indicated. When the third output data is set to active, the button deselection is indicated. The mute status signal 580 provides fourth output data (e.g. microphone status data or more broadly sensor status data) indicating the status of the sensor (e.g. disabled corresponding to the mute state or enabled corresponding to the sensing state). A single bit can be used for this indication. For instance, when the fourth output data is set to inactive, the sensor disabling is indicated. When the fourth output data is set to active, the sensor enabling is indicated. The light source on/off signal 590 provides light ON data and light OFF data. The light ON data indicates that the light source should emit light. The button off data indicates that the light source should not emit light. The light source intensity signal 595 provides the light intensity data indicating the light intensity setting of the light source for the light emission.

Each one of the input data corresponding to the signals 510-540 can be received at a data input terminal of the mute controller 500. As further illustrated in FIG. 6, each data input terminal can be an input pin. Conversely, each one of the output data corresponding to the signals 550-595 can be output from a data output terminal of the mute controller 500 to data input terminals of the respective components. As further illustrated in FIG. 6, each data output terminal can be an output pin. In particular, the output data of the mute state signal (A) 550 is output to a data input terminal of a first switch of the switch set (e.g., a power switch). The output data of the mute state signal (B) 560 is output to a data input terminal of a second switch of the switch set (e.g., a data switch). The output data of the button selection signal 570 and the output data of the mute status signal 580 are output to two different data input terminals of the SoC. The output data of the light source on/off signal 590 and the output data of the light source intensity signal 595 to the light source are also output to two different data input terminals of the light source.

FIGS. 6A and 6B illustrates an example of components of a mute controller 600, according to embodiments of the present disclosure. As illustrated, the mute controller 600 is implemented in hardware and includes a set of logic gates. The mute controller 600 is an example implementation of the mute controller 500 of FIG. 5, although other implementations are likewise possible.

Starting with the bottom left of FIG. 6A, the mute controller 600 includes a first input pin that receives a light source intensity signal from an SoC. The first input pin is connected directly to a first output pin, such that the light source intensity signal is passed through to the first output pin. The first output pin outputs the light source intensity signal to a light source. Among the pass through pass, the inputted light source intensity signal may be inverted before being outputted.

Next, the mute controller 600 includes a second input pin and a third input pin. The second input pin receives a mute setting signal from the SoC. The third input pin receives a light source voltage feedback signal from the light source. The third input pin is connected to a comparator that compares the indicated voltage value to a reference voltage value (e.g., eight-hundred millivolts). The mute setting signal can be delayed and passed through a register and input to an XOR gate, along with an output of the comparator. The output of comparator can also be passed through the register. The output of the XOR gate can be passed through a register and provided for further processing with other signals to output pins of the mute controller 600 (e.g., as mute status signal and mute state signal (B)).

The mute controller 600 includes a fourth input pin. The fourth input pin receives a mute button signal from a mute button. The mute button signal can be passed through directly to an output pin of the mute controller 600 for output as a button selection signal. The mute button signal can be further processed by other processing components of the mute controller 600 includes a timer, a set of delay buffers, registers, D-type flip flops, path selectors, the XOR gate and provided to another output pin of the mute controller as a mute status signal.

FIG. 7 illustrates an example of a power control system 700 and a data control system 705, according to embodiments of the present disclosure. The power control system 700 and the data control system 705 form a switch set that is configured as a gating peripheral for a sensor, such as a microphone. The switch set is an example of the switch set 360 of FIG. 3 and the switch set 460 of FIG. 4.

In an example, the power control system 700 receives a mute state signal (A) 710. When the mute state signal (A) 710 is set to a high voltage (e.g., representing a “1” bit to indicate the mute state), the power control system 700 creates an open circuit 750 in a power line to the microphone. Otherwise, the power control system 700 closes the circuit. The power control system 700 can be implemented as a p-channel field-effect transistor (PFET transistor), with its gate receiving the mute state signal (A) 710, its source connected to a power source, and its drain connected to the microphone.

In an example, the data control system 705 receives a mute state signal (B) 720. The mute state signal (B) 720 is an invert of the mute state signal (A) 710. In addition, the data control system 705 receives audio data of the microphone (e.g., one of the inputs to the data control system 705 is connected to an output of the microphone). When the mute state signal (B) 720 is set to a low voltage (e.g., representing a “0” bit to indicate the mute state), the data control system 705 zeros the output to the data line to the SoC. Otherwise, the audio data is passed on the data line. The data control system 705 can be implemented as a tri-state buffer, with its third input connected to a power source.

FIG. 8 illustrates another example of a power control system 800 and a data control system 805, according to embodiments of the present disclosure. The power control system 800 and the data control system 805 form a switch set that is configured as a gating peripheral for a sensor, such as a camera. The switch set is an example of the switch set 470 of FIG. 4.

In an example, the power control system 800 receives a mute state signal (A) 810 and a power signal 820. The power signal 820 is received from a SoC and indicates whether the camera power is enabled or not. When the mute state signal (A) 810 is set to a high voltage (e.g., representing a “1” bit to indicate the mute state) and the power signal is set to a low voltage (e.g., representing a “0” bit to indicate that the camera power is enabled), the power control system 800 creates an open circuit 850 in a power line to the camera. Also when the mute state signal (A) 810 is set to the high voltage and the power signal is set to a high voltage (e.g., representing a “1” bit to indicate that the camera power is disabled), the power control system 800 creates the open circuit 850. Otherwise, the power control system 800 closes the circuit. The power control system 800 can be implemented as a NOR gate in series with a load switch. The mute state signal (A) 810 and the power signal 820 are input to the NOR gate, the output of which is sent as a camera power enable signal as an input to the load switch. The load switch couples and decouples the camera with a power source based on the camera power enable signal.

In an example, the data control system 805 receives a mute state signal (B) 830. The mute state signal (B) 830 is an invert of the mute state signal (A) 810. A low voltage “L” of the mute state signal (B) 830 indicates the request for the mute state. In addition, the data control system 805 receives a camera enable signal from the SoC. The camera enable signal indicates whether the camera is enabled (e.g. when this signal is set to a high voltage “H” indicating a camera enable data set as “1” bit) or disabled (e.g., when this signal is set to a low voltage “L” indicating the camera enable data set as “a “0” bit). When any of the mute state signal (B) 820 or the camera enable signal is low, the data control system 805 outputs an override signal 860 to the SoC. The override signal 860 includes a camera disable signal (e.g., a camera disabled status). Otherwise, no override signal 860 is output and, instead, the data control system 805 continues to send a camera enable signal. The data control system 805 can be implemented as an AND gate.

FIG. 9 illustrates an example of a user interface, according to embodiments of the present disclosure. As illustrated, the user interface is a light source 900, although other types of the user interface are similarly possible. The light source 900 includes a first switch 910, a first resistor set (shown as a resistor 915A and a resistor 915B), an LED 920, a second resistor set (shown as a resistor 930A and a resistor 930B), a second switch 940, a third resistor set (shown as a resistor 950), a fourth resistor set (shown as resistor 960).

The first switch 910 can be implemented as PFET and the second switch 940 can be implemented as a n-type FET transistor (NFET). The first switch 910 is connected to a power source 902 of the light source 900 and receives a light source intensity signal 904 from a mute controller. The second switch 940 receives a light source on/off source signal 906 from the mute controller. When the source signal 906 from the mute controller is set to a high voltage (e.g., indicating that the LED 920 is to be powered on), the second switch 940 enables current to flow to the LED 920 from the power source 902 via the first switch 910. The setting of this current flow is set according to the light source intensity signal 904. Otherwise, the second switch disables the current flow.

The resistor 915A is also connected to the power source 902 and has a higher resistance compared to the resistor 915B (e.g., between one-thousand and ten-thousand ohms, in comparison to between ten and one-hundred ohms). Both resistors 915A and 915B are connected to an anode of the LED 920. The resistor 930A and the resistor 930B may have similar resistance (e.g., between five-hundred thousand ohms and two-million ohms). Whereas the resistor 930B is connected to the ground, the resistor 930A is connected to a cathode of the LED 920. The voltage value at the resistor indicates a voltage value at the cathode when no current is flowing through the first switch 910 and the second switch 940. This voltage value should be minimal (e.g., below a voltage threshold corresponding to the minimum value of the cathode voltage indicating that the LED 920 is emitting visible light) when the LED 920 has no failure. Otherwise, the voltage value indicates a failure. The voltage value is output as a light source voltage feedback signal 908 to the mute controller. In another example, the voltage value between the resistor 930A and the resistor 930B is output as the light source voltage feedback signal 908 to the mute controller. The resistor 950 is connected to a power source 903 and the cathode of the LED 920. The resistor 960 is connected to the input of the switch 940 and the ground.

Although FIG. 9 illustrates that the light source 900 includes a single LED 920, a single first resistor set, and a single second resistor set, other configurations of the light source 900 are possible. For example, for redundancy, the light source includes a second LED, two first resistor sets each connected to one of the LEDs, and two second resistor sets each connected to one of the LEDs.

FIGS. 10-13 illustrate flows for controlling one or more sensors of a computing device. The computing device can be any of the computing device 100 of FIG. 1 or the computing device 200 of FIG. 2. The operations of the flow can be performed by a mute controller of the computing device. The mute controller can be any of the mute controller 350 of FIG. 3, the mute controller 450 of FIG. 4, the mute controller 500 of FIG. 5, or the mute controller 600 of FIG. 6.

FIG. 10 illustrates an example of a flow for controlling one on more sensing states of the one or more sensors, according to embodiments of the present disclosure. In an example, the flow starts at operation 1002, where the mute controller receives a mute button signal. For example, the mute button signal corresponds to the mute button signal 510 of FIG. 5 and is received as a first input signal from a mute button of the computing device.

At operation 1004, the mute controller receives a mute setting signal. For example, the mute setting signal corresponds to the mute setting signal 520 of FIG. 5 and is received as a second input signal from an SoC of the computing device.

At operation 1006, the mute controller receives a light source voltage feedback signal. For example, the light source voltage feedback signal corresponds to the light source voltage feedback signal 540 of FIG. 5 and is received as a third input signal from a light source of the computing device.

At operation 1008, the mute controller receives a light source intensity signal. For example, the light source intensity signal corresponds to the light source intensity signal 530 of FIG. 5 and is received as fourth input signal from the SoC.

At operation 1010, the mute controller determines and stores mute state of the computing device. For example, and as described in connection with FIG. 5, the mute controller implements logic, in hardware and/or software, to generate output signals based on the input signals. The output signals reflect the determination of the mute state. Generally, the logic uses the mute button signal as a control to enter into the mute state and exit from the mute state back into a sensing state. The mute state can be stored as an indication (e.g., a flag), where one value of the indication indicates the mute state and another value indicates the sensing state. The logic uses also the light source voltage feedback signal to force the mute state upon detection of a failure in the light source. Once the mute state is entered, the SoC is prevented from changing the operational state back to the sensing state. In other words, the mute setting signal from the SoC is not usable to transition to the sensing state and only the mute button signal or the light source intensity signal (upon detection that the failure no longer exists) are usable for the transition to the sensing state.

At operation 1012, the mute controller outputs a light source intensity signal. For example, the light source intensity signal corresponds to the source setting signal 595 of FIG. 5, is a pass through of the fourth input signal, and is sent as a first output signal to the light source.

At operation 1014, the mute controller outputs a button selection signal. For example, the button selection signal corresponds to the button selection signal 570 of FIG. 5, is not delayed by a delay time interval, and is sent as a second output signal to the SoC.

At operation 1016, the mute controller outputs a mute status signal. For example, the mute status signal corresponds to the mute status signal 580 of FIG. 5, is delayed by the delay time interval relative to the button selection signal output at operation 514, and is sent as a third output signal to the SoC.

At operation 1018, the mute controller outputs a mute state signal. For example, the mute state signal corresponds to the mute state signal (A) 550 of FIG. 5, is also delayed by the delay time interval relative to the button selection signal output at operation 514, and is sent as a fourth output signal to a switch set coupled with a sensor of the computing device.

At operation 1020, the mute controller outputs a redundant mute state signal. For example, the redundant mute state signal corresponds to the mute state signal (b) 560 of FIG. 5, is also delayed by the delay time interval relative to the button selection signal output at operation 514, and is sent as a fifth output signal to the switch set.

FIG. 11 illustrates an example of a flow for controlling a sensor based on a mute button signal, according to embodiments of the present disclosure. In an example, the flow starts at operation 1102, where the mute controller receives a mute button signal. For instance, the mute button signal is received from a button of the computing device and includes button ON data indicating an activation (e.g., push) of the button, where the activation corresponds to a request to disable the sensor (e.g., for the mute state).

At operation 1104, the mute controller sends an indication of the activation of the button to the SoC. Optionally, In response, the SoC may output a message (e.g., via a speaker or a GUI) requesting a user confirmation to mute the sensor. If the confirmation is received, the SoC can output a mute setting signal to the mute controller requesting the sensor to be disabled.

At operation 1106, the mute controller determines whether a time duration of the activation (e.g., push) is smaller than a predefined time length. In an example, upon receiving the mute button signal, the mute controller starts a timer and, upon receiving a change to the mute button signal (e.g., this signal changes to include button OFF data), the mute controller stops the time. The time duration between the start and the stop is compared to the predefined time length. If smaller, operation 1108 follows operation 1106. Otherwise, operation 1114 is performed and, in this example, the long button activation (e.g., long button push) can correspond to a powering off of the device. In an alternate example, upon a time duration longer than the predefined time length, operation 1108 follows operation 1106.

At operation 1108, the mute controller determines whether the sensor is already in the mute state or not. For instance, the mute controller stores an indication of the state (e.g., as a flag). And the mute state is determined from the stored indication. In another illustration, the mute controller determines whether the mute controller is already outputting controls to disable the sensor (e.g., a mute state signal to a power switch and the same or a redundant mute signal to a data switch). If the sensor is already in the mute state, operation 1112 follows operation 1108. Otherwise, operation 1110 is performed.

At operation 1110, the mute controller causes the sensor to be disabled. For instance, the mute controller sends first output data to a power switch that couples the sensor and the power source. The first output data causes the power switch to decouple the sensor from the power source. The mute controller also sends second output data to a data switch that couples the sensor and the SoC. The second output data causes the data switch to decouple the sensor from the SoC via. In addition, the mute controller sends, to the SoC, third output data indicating the activation (e.g., push) of the button and fourth output data indicating that the sensor is disabled, where the first, second, and fourth output data can be send after a time delay relative to the third output data. Further, the mute controller sends fifth output data to the light source, where the fifth output data includes light ON data indicating that the light source should emit light.

At operation 1112, the sensor is currently disabled and the button has been selected again (e.g., to request the sensor to be re-enabled). Accordingly, the mute controller continues causes the sensor to be re-enabled. For instance, the mute controller controls over the switches to couple the sensor to the power source and stop the blanking of the sensor's output, over the light source to stop the light emission, and indicates to the SoC, that the sensor is enabled.

At operation 1114, the mute controller does not perform an action. Accordingly, the sensor remains in its current operational state.

FIG. 12 illustrates an example of a flow for controlling a sensor based on a light source voltage feedback signal, according to embodiments of the present disclosure. Operations of the flow of FIG. 12 may be performed following the reception of input data indicating a request to enable the sensor and the enabling of the sensor based on this input data.

In an example, the flow starts at operation 1202, where the mute controller a light source voltage feedback signal from the light source. The light source voltage feedback signal indicates a voltage value at the light source.

At operation 1204, the mute controller determines whether a failure of the light source exists or not. The failure can correspond to the light source emitting light indicating the mute state, while the sensor is still enabled (e.g., following the disabling of the sensor per the flow of FIG. 11, the input data can be received requesting the enabling of the sensor, and the sensor is enabled accordingly. Thereafter, the failure of the light source may occur). The mute controller can compare the voltage value to a reference voltage that corresponds to the minimum voltage at which visible light emission can occur. If larger than the reference voltage, the failure is detected and operation 1206 follows operation 1204. Otherwise, operation 1220 is performed.

At operation 1206, the mute controller determines whether the sensor is already in the mute state or not. For instance, the mute controller stores an indication of the state (e.g., as a flag). And the mute state is determined from the stored indication. In another illustration, the mute controller determines whether the mute controller is already outputting controls to disable the sensor (e.g., a mute state signal to a power switch and the same or a redundant mute signal to a data switch). If the sensor is already in the mute state, operation 1210 follows operation 1206. Otherwise, operation 1208 is performed.

At operation 1208, the mute controller causes the sensor to be disabled. For instance, the mute controller sends the five output data described herein above in connection with operation 1108.

At operation 1210, the sensor is already disabled and the mute controller continues causing the sensor to be disabled. For instance, the mute controller continues to send the five output data and does not send other output data that causes the sensor to be enabled.

At operation 1220, the sensor is already enabled and the mute controller continues causing the sensor to be enabled. For instance, the mute controller does not change controls over the power switch, data switch, SoC, and light source.

FIG. 13 illustrates an example of a flow for controlling a sensor based on a mute setting signal, according to embodiments of the present disclosure. In an example, the flow starts at operation 1302, where the mute controller receives a mute setting signal to disable the sensor. For instance, the mute setting signal is received as input data from the SoC and indicates a request to the disable the sensor.

At operation 1304, the mute controller determines whether the sensor is already in the mute state or not. For instance, the mute controller stores an indication of the state (e.g., as a flag). And the mute state is determined from the stored indication. In another illustration, the mute controller determines whether the mute controller is already outputting controls to disable the sensor (e.g., a mute state signal to a power switch and the same or a redundant mute signal to a data switch). If the sensor is already in the mute state, operation 1308 follows operation 1304. Otherwise, operation 1306 is performed.

At operation 1306, the mute controller causes the sensor to be disabled. For instance, the mute controller sends the five output data described herein above in connection with operation 1108.

At operation 1308, the sensor is already disabled and the mute controller continues causing the sensor to be disabled. For instance, the mute controller continues to send the five output data described or does not send other output data that causes the sensor to be enabled.

At operation 1310, the mute controller receives a request to enable the sensor. For instance, the request is received based on an activation (e.g., push) of the button, resulting in a mute button signal to enable the sensor.

At operation 1312, the mute controller determines whether a light source failure exists or not. This determination can be made according to the voltage value indicated by the light source voltage feedback signal. If the failure exists, the mute controller may not enable the sensor in response to the request from the button and operation 1308 follows operation 1312. Otherwise, the sensor can be enabled. Accordingly, operation 1314 follows operation 1312.

At operation 1314, the mute controller causes the sensor to be enabled. For instance, the mute controller sends first output data to the power switch to couple the sensor to the power source. The mute controller sends second output data to the data switch to couple the sensor to the SoC. The mute controller also sends third output data to the SoC indicating that the sensor is enabled and sends fourth output data to the light source to stop the light emission.

FIG. 14 illustrates an example of a computing device that includes multiple clients and a mute control system, according to embodiments of the present disclosure. As illustrated, the computing device includes a button 1410, a mute control system 1420, and a client system 1430. Although not shown, the computing device also includes a set of sensors and a user interface. The button 1410 can be a physical button or a non-reprogrammable button (e.g., implemented with non-programmable firmware stored in a read-only memory), as described herein above, and is operable, upon activation, to disable the set of sensors and, upon deactivation, to enable the set of sensors. The mute control system 1420 includes a mute controller and a set of switches, each corresponding to a sensor. The mute control system 1420 is operable to, upon the activation of the button 1410 and/or an input signal from the user interface, disable the set of sensors by decoupling them, via the set of switches, from a power source and from a processor. The processor can be included in the client system 1430.

The client system 1430 includes multiple clients, each of which can be implemented in hardware and/or software, as further described in FIGS. 16-17. Generally, a client receives sensor data generated by at least one sensor of the computing device and provides functionalities based on the received sensor data. When the sensor(s) is disabled, the client is notified of the disabling such that the functionalities can be properly interrupted, modified, and/or an alert is provided to a subscriber (e.g., another client) or a user of the computing device.

In the example illustrated in FIG. 14, the client system 1430 includes multiple voice clients 1440A-1440K, multiple video clients 1450A-1450L, and other types of clients, each generally shown as a sensor client 1460. A voice client receives audio data from a microphone of the computing device and provides audio-related functionalities. For instance, the microphone can receive speech input from the user and generate audio data representative of the speech input. The voice client receives the audio data for further processing, or some of the processing can be performed by the processor and/or a remote server in communication with the computing device and the voice client receives processed audio data. The processing includes but is not limited to, for instance, detecting voice activity, detecting a wake word, performing natural language processing, generating a command, and/or controlling the functionalities of the voice client. Similarly, a video client receives video data from a camera of the computing device and, optionally audio data from the microphone, and provides video-related functionalities. Upon the camera generating the video data, the video client receives the video data for further processing, or some of the processing can be performed by the processor and/or the remote server and the video client receives processed video data. The processing includes, for instance, detecting an object, adding an overlay, formatting the video data for display, and/or controlling the functionalities of the video client.

Generally, a sensor client, whether an audio client, a video client, or another type of sensor client, receives data corresponding to sensor data generated by a sensor of the computing device (e.g., whether the microphone, the camera, a motion sensor, an infrared sensor, a proximity sensor, a temperature sensor, a Lidar sensor, etc.) and provides sensor-related functionalities. The data received by the sensor client can include the sensor data, where this sensor data can be sent by the sensor directly to the voice client via a data line that couples the sensor and the sensor or indirectly through an intermediary component that is coupled between the sensor and the sensor client, such as through an SoC. Additionally or alternatively, the data received by the sensor client can include data that is processed by the intermediary device from the sensor data that the intermediary device receives from the sensor. In both cases, upon receiving the data, the sensor further processes this received data according to the functionalities that the sensor client supports.

Upon a button activation 1412 of the button 1410, the mute control system 1420 generates and sends a mute status signal 1422 to the client system 1430. In particular, the button activation 1412 results in a mute button signal being sent from the button 1410 to the mute control system 1420, similar to the mute button signal 510 of FIG. 5. The mute status signal 1422 can correspond to the mute status signal 580 of FIG. 5 and can include mute status data indicating that the set of sensors of the computing device is disabled. The client system 1430 receives the mute status signal 1422 and, distributes to each of the voice clients 1440A-1440K, video clients 1450A-1450L, and the one or more sensor clients 1460, notification data indicating that the set of sensors is disabled.

Conversely, upon a deactivation of the button 1410, the mute control system 1420 sends an updated mute status signal to the client system 1430 indicating that the set of sensors is enabled. In turn, the client system 1430 distributes, to each of the voice clients 1440A-1440K, video clients 1450A-1450L, and the one or more sensor clients 1460, notification data indicating that the set of sensors is enabled.

Similarly, upon detecting a failure in a user interface of the computing device (e.g., when a light source is emitting light indicating that the set of sensors is disabled, while the set of sensors is in fact enabled), the mute control system 1420 can disable the set of sensors. This disabling also results in the transmission of the mute status signal 1422 and the resulting transmission of notification data to each of the voice clients 1440A-1440K, video clients 1450A-1450L, and the one or more sensor clients 1460.

When the computing device is in the sensing state (e.g., the set of sensors is enabled), any of the voice clients 1440A-1440K, video clients 1450A-1450L, and the one or more sensor clients 1460 can request the mute state (e.g., the set of sensors to be disabled). In this case, the client system 1430 sends a mute request 1432 to the mute control system 1420 indicating a request to disable the set of sensors. The mute request 1432 can include output data indicating this request and can correspond to the mute setting signal 520 of FIG. 5.

For instance, the computing device can be installed in a vehicle, such as being integrated in the vehicle's infotainment system. In this case, the voice client (A) 1440A corresponds to a smart speaker capable of, among other things, playing music in response to a first wake word (e.g., “Alexa”). The voice client (K) 1140K corresponds to a vehicle personal assistance capable of, among other things, displaying route navigation in response to a second wake word (e.g., “Car”). The video client (A) 1450A corresponds to a camera system capable of, among other things, displaying a video of the surrounding of the vehicle. And the sensor client 1450 can be a temperature sensor capable of, among other things, measuring a cabin temperature of the vehicle for climate control.

Accordingly, upon the button activation 1412, the microphone, the camera, and the temperature sensor are disabled and the voice client (A) 1440A, the voice client (K) 1440(K), the video client (A) 1450A, and the sensor client 1450 are notified of the mute state. In response, the video client (A) may display on a screen of the infotainment system that the infotainment system is muted. At a different time, and when the different sensors are enabled, a driver of the vehicle can utter “Alexa, play music.” Based on audio data generated by the microphone about this utterance, the voice client (A) 1440A can direct client system 1430 output music on a speaker of the infotainment system. Upon another utterance of “Car, show my location on the map,” and based on audio data generated by the microphone about this utterance, the voice client (B) 1440B can direct client system 1430 display the location on the map on the screen of the infotainment system. Upon a further utterance of “Alexa, mute,” and based on audio data generated by the microphone about this utterance, the client system 1430 can sent the mute request 1432 to the mute control system 1420. In turn, the mute control system 1420 disables the microphone, camera, and the temperature sensor and sends the mute status signal 1422 to the client system 1430. In response, the client system 1430 sends notification data about this disabling to the voice client (A) 1440A, the voice client (K) 1440(K), the video client (A) 1450A, and the sensor client 1460. And the video client (A) may direct the client system 1430 to display on a screen of the infotainment system that the infotainment system is muted.

FIG. 15 illustrates an example of a diagram of a computing device 1500 that includes multiple clients and a mute control system, according to embodiments of the present disclosure. As illustrated, the computing device 1500 includes a button 1510, a microphone 1520, a light source 1530, a client system 1540, a mute controller 1550, a switch set 1560 (including a power control system 1562 and a data control system 1564), and a power source 1580. Each of the button 1510, microphone 1520, light source 1530, mute controller 1550, switch set 1560, and power source 1580 is similar to the button 310, microphone 320, light source 330, mute controller 350, switch set 360, and power source 380, respectively, of FIG. 3 and the similarities are not repeated herein in the interest of brevity. Rather than including an SoC 340 as in the computing device 300 of FIG. 3, the computing device 1500 includes the client system 1540. The client system 1540 can include an SoC 1542 (or more generally a processor or a microcontroller) and additional components that are implemented on the SoC 1542 or implemented separately from the SoC 1542 as further described in connection with FIGS. 16-17. These components include a distributor 1544, an aggregator 1546, and voice clients 1548.

The client system 1540 receives a mute status signal and a button selection signal from the mute controller 1550, similar to the mute status signal 580 and the button selection signal 570, respectively, of FIG. 5. These signals can be received at different input terminals of the client system 1540 and can include output data from the mute controller 1550. The client system 1540 also sends a mute setting signal and a light source intensity signal to the mute controller 1550, similar to the mute setting signal 520 and the light source intensity signal 530, respectively, of FIG. 5. These signals can be sent from different output terminals of the client system 1540 and can include input data to the mute controller 1550.

The distributor 1544 receives the mute status signal, or the output data included therein and indicating a mute status of the microphone 1520 (e.g., including microphone status data or, more broadly, sensor status data). The distributor 1544 can generate notification data indicating this mute status and send the notification data to the voice clients 1548. In an example, the notification data is sent in a broadcast to the voice clients 1548 according to a push mechanism. In another example, the distributor 1544 stores the received output data or the mute status in a memory of the computing device 1500 (e.g., in a buffer). Upon receiving a request from a voice client for the status of the microphone 1512, the distributor 1544 generates and sends the notification data based on the stored data in a response to the voice client according to a pull mechanism.

In comparison, the aggregator 1546 aggregates requests from the voice clients 1548 for disabling the microphone 1520. In particular, while the microphone 1520 is enabled, the aggregator 1546 receives output data from at least one voice client requesting the disabling the microphone 1520. If such output data is received from multiple ones of the voice clients 1548, the aggregator 1546 generates and sends a unified request (e.g., also as output data) for disabling the microphone 1520 (e.g., this request can be included in the mute setting signal). If such request has been sent out and yet another disabling request is received from a voice client, the aggregator 1546 may, but need no, generate and send a corresponding disabling request. While the microphone 1520 is disabled, if the aggregator 1546 receives a disabling request from a voice client, the aggregator 1546 can ignore this request.

Although FIG. 15 illustrates a computing device that includes a single sensor (e.g., a microphone) and a single client system that includes corresponding sensor clients (e.g., voice clients), other implementation of the computing device are possible. For example, the computing device can include multiple sensors, some or all of which can be of different types (e.g., a microphone and a camera). In this case, for each sensor, the computing device can include a corresponding switch set. In addition and for each sensor, the computing device can include a corresponding set of sensor clients, where these sensor clients can be implemented on a single client system or can be distributed between multiple client systems of the computing device. If multiple client systems are used, each of such systems can receive the mute status signal and, optionally, the button selection signal from the mute controller 1550 and send a mute setting signal to the mute controller 1550. Further, one distributor and one aggregator can be used to support the different client systems or each of the client system can include its own distributor and aggregator.

FIG. 16 illustrates an example of notifying multiple clients included in a computing device about a disabling of a sensor, according to embodiments of the present disclosure. As illustrated in FIG. 16, the computing device includes an SoC 1610 (or, more generally, a processor) that implements a distributor 1620, aggregator 1630, and multiple sensor clients 1640A-1640K. The SoC 1610 corresponds to the client system 1540 of FIG. 15.

In an example, each of the distributor 1620, aggregator 1630, and sensor clients 1640A-1640K is implemented as a separate software application executing on the SoC 1610. Data can be communicated between the software applications via application programming interfaces (APIs).

At a data input terminal of the SoC 1610, a mute status signal 1612 is received. The mute status signal 1612 includes output data from a mute controller and indicates whether a set of sensors of the computing device is disabled or enabled. The distributor 1620 receives this data and, optionally, stores it or stores an indication of the status (e.g., as a flag set to one for disabled and to zero for enabled). To each of the sensor clients 1640A-1640K, the distributor 1620 sends notification data via the respective API, where the notification data indicates the status.

At one or more data input terminals of the SoC 1610, sensor data is received from the set of sensors. The sensor data can be further processed by the SoC 1610, sent to another components of the computing device and/or to a remote server and received back as processed sensor data. The sensor data, as received from the sensor set, and/or as further processed is sent to one or more of the sensor clients 1640A-140K as applicable.

In addition, any of the sensor clients 1640A-1640K can output a request to disable the set of sensors. The corresponding request data is output from the applicable sensor client(s) via the respective API(s) to the aggregator 1630. The aggregator 1630 implements an OR logic by performing OR operations on the received request data from the applicable sensor clients 1640A-1640K, such that if any of the sensor clients 1640A-1640K requests the disabling, the aggregator 1630 outputs a mute request 1614.

FIG. 17 illustrates another example of notifying multiple clients included in a computing device about a disabling of a sensor, according to embodiments of the present disclosure. As illustrated in FIG. 17, the computing device includes an SoC 1710 (or, more generally, a processor) and a distributor 1720, aggregator 1730, and multiple sensor clients 1740A-1740K that are separate from the SoC 1710. The SoC 1710, distributor 1720, aggregator 1730, and sensor clients 1740A-1740K correspond to the client system 1540 of FIG. 15.

In an example, each of the distributor 1720, aggregator 1730, and sensor clients 1740A-1740 is implemented as a separate hardware component. Optionally, some of the functionalities of the distributor 1720, aggregator 1730, and sensor clients 1740A-1740 can be implemented on the SoC 1710 in a distributed architecture. For instance, one of the sensor clients 1740A-1740K is a voice client. The hardware implementation of the voice client includes a digital signal processor (DSP), and output data of the DSP can be further processed by an application of the voice client executing on the SoC 1710.

In an example, a data input terminal of the distributor 1720 and a data input terminal of the SoC 1710 receive a mute status signal 1712. The mute status signal 1712 includes output data from a mute controller and indicates whether a set of sensors of the computing device is disabled or enabled. The distributor 1720 receives this data and, optionally, stores it or stores an indication of the status in a buffer of the distributor 1720. A single output terminal of the distributor 1720 can be connected to data input terminals of the sensor clients 1740A-1740K. Alternatively, each of the sensor clients 1740A-1740K is connected to at least one different output terminal of the distributor 1720. In both cases, the distributor 1720 sends notification data via the applicable output terminal in a pull or push mechanism, where the notification data indicates the status.

Each of the sensor clients 1740A-1740K can include a DSP, analog to digital converter and/or digital to analog converter, a filter, an amplifier, a microprocessor, a memory, and/or other computing components that processor sensor data in support of functionalities of the sensor clients. The sensor client can include one or more data input terminals to receive sensor data. The sensor data can be received from the SoC 1710 (as illustrated with the dashed lines in FIG. 17), from the distributor 1720, and/or from a sensor. In a distributed architecture where some of the functionalities of the sensor client is implemented on the SoC, one or more output terminals of the sensor client are connected to one or more data input terminals of the SoC 1720 to send processed data to the SoC 1720 (as illustrated with the double sided arrow in FIG. 17).

In addition, any of the sensor clients 1740A-1740K can output a request to disable the set of sensors. For each of such sensor clients, the corresponding request data is output via an output terminal of the sensor client to a data input terminal of the aggregator 1730. Similarly to the distributor 1730, the same data input terminal of the aggregator 1730 is connected to the different sensor clients 1740A-1740K or one data input terminal is connected per sensor client. In one example, the SoC 1710 can also output a request to disable the set of sensors. This output can be sent directly to the aggregator 1730 or to one or more of the sensor clients 1740A-1740K that relay the output forward to the aggregator 1730. The aggregator 1730 implements a set of OR gates to perform OR operations on the received request data from the applicable sensor clients 1740A-1740K and, as applicable, the SoC 1710, such that if any of the sensor clients 1740A-1440K or, as applicable, the SOC 1710 requests the disabling, the aggregator 1730 outputs a mute request 1714.

FIG. 18 illustrates an example of a flow for notifying multiple clients included in a computing device about a disabling of a sensor, according to embodiments of the present disclosure. The computing device can be any of the computing devices described in connection with FIGS. 14-17. The computing device includes a mute control system and a client system. Some of the operations of the flow can be performed by a mute controller of the mute control system and other operations of the flow can be performed by a distributor, aggregator, and/or one or more sensor clients of the client system.

In an example, the flow starts at operation 1802, where the computing device receives input data indicating a request to disable a sensor (or a set of sensors as described herein above). The input data can be received upon an activation of a button, such as data in a mute button signal. The input data can be received upon a detection of a failure of a user interface of the computing device, whereby, for instance, a light source voltage feedback signal indicates that a light source is emitting light while the sensor is enabled. Alternatively, the input data can be received from an aggregator of the computing device and can correspond to a request from one or more of the sensor clients for the disabling of the sensor.

At operation 1804, the computing device determines whether the sensor is to be disabled or not. For instance, if the sensor is enabled and the input data is received, the computing device determines that the sensor is to be disabled, whereby operation 1806 follows operation 1804. If the sensor is already disabled, the computing device can ignore the input request, whereby the flow may loop back to operation 1802 and/or may include outputting a notification (e.g., a chime on a speaker, a text on a GUI) that the sensor is already disabled.

At operation 1806, the computing device disables the sensor 1806. As described herein above in connections with FIGS. 3, 4, and 15, the mute controller can send the relevant output data to the switches, causing the switches to decouple the sensor from a power source and to blank the sensor's data output. The mute controller can also send the relevant output data to the user interface about the sensor being disabled, causing the user interface to output an indication of this disabling. When including a light source, the mute controller can also send data about the light intensity of the light source. The mute controller can also send the relevant output data to the SoC about the button activation, as applicable, and to the SoC and, as applicable, the distributor about the sensor being disabled (e.g., sensor mute status data).

At operation 1808, the computing device sends notification to data to the sensor clients, where the notification data indicates that the sensor is disabled. For instance, the distributor receives the sensor mute status data from the mute controller directly or via the SoC and sends, accordingly to a push mechanism or a pull mechanism, the notification data to each of the sensor clients.

At operation 1810, the computing device outputs the indication of the sensor being disabled. For instance, the user interface outputs this indication based on the data received from the mute controller at operation 1806.

At operation 1812, the computing device receives input data indicating a request to enable the sensor. The input data can be received upon a deactivation of a button, such as data in an updated mute button signal.

At operation 1814, the computing device determines whether the sensor is to be enabled or not. Different factors can be considered in this determination. For instance, if the mute state was entered because of a button activation, the sensing state can be transitioned back to upon the input data corresponding to the button activation but not to the request from the one or more sensor clients. In this way, the sensor clients cannot re-enable the sensor when the sensor was disabled based on the activation of the button. In another illustration, if the mute state was entered based on the input data corresponding to a disabling request from a sensor client, the mute controller can determine that the sensor can be enabled upon the input data at operation 1814 corresponding to the deactivation of the button. If the mute state was entered because of a failure of the user interface, the mute state is latched and the sensing state cannot be transitioned back until the failure is detected to no longer be occurring. Alternatively, the button deactivation can override the failure latching. If the determination is that the sensor is to be enabled, operation 1816 follows operation 1814. Otherwise, the flow loops back to operation 1810, whereby the sensor remains disabled and the indication of the mute state continues to be presented. Optionally, the flow may include outputting a notification (e.g., a chime on a speaker, a text on a GUI) that the sensor cannot be enabled.

At operation 1816, the computing device enables the sensor. As described herein above in connections with FIGS. 3, 4, and 15, the mute controller can send the relevant output data to the switches, causing the switches to re-couple the sensor with the power source and to stop the blanking of the sensor's data output. The mute controller can also send the relevant output data to the user interface about the sensor being enabled, causing the user interface to stop outputting the indication of this disabling and/or to output an indication that the sensor is re-enabled. The mute controller can also send the relevant output data to the SoC and, as applicable, the distributor about the sensor being enabled (e.g., updated sensor mute status data).

At operation 1818, the computing device sends notification data to the to the sensor clients, where the notification data indicates that the sensor is enabled. For instance, the distributor receives the sensor mute status data from the mute controller directly or via the SoC and sends, according to the push mechanism or pull mechanism, the notification data to each of the sensor clients.

At operation 1820, the computing device stops outputting the indication that the sensor is disabled and, optionally, outputs an updated indication that the sensor is re-enabled. For instance, the user interface stops the disabling indication and, optionally, outputs the enabling indication based on the data received from the mute controller at operation 1816.

FIG. 19 illustrates an example of an architecture of a computing device 1900 that includes a mute control system 1914, according to embodiments of the present disclosure. The mute control system 1914 can include a mute button, a mute controller, and one or more switch sets similar to the components of the computing devices described herein above. Although the components of the computing device 1900 are illustrated as belonging to a same computing device 1900, the computing device 1900 can also be distributed (e.g., between multiple user devices).

The computing device 1900 includes at least a processor 1902, a memory 1904, a storage device 1906, input/output peripherals (I/O) 1908, communication peripherals 1910, an interface bus 1912, and the mute controls system 1914. The interface bus 1912 is configured to communicate, transmit, and transfer data, controls, and commands among the various components of the computing device 1900. The memory 1904 and the storage device 1906 include computer-readable storage media, such as RAM, ROM, electrically erasable programmable read-only memory (EEPROM), hard drives, CD-ROMs, optical storage devices, magnetic storage devices, electronic non-volatile computer storage, for example Flash® memory, and other tangible storage media. Any of such computer readable storage media can be configured to store instructions or program codes embodying aspects of the disclosure. The memory 1904 and the storage device 1906 also include computer readable signal media. A computer readable signal medium includes a propagated data signal with computer readable program code embodied therein. Such a propagated signal takes any of a variety of forms including, but not limited to, electromagnetic, optical, or any combination thereof. A computer readable signal medium includes any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use in connection with the computing device 1900.

Further, the memory 1904 includes an operating system, programs, and applications. The processor 1902 is configured to execute the stored instructions and includes, for example, a logical processing unit, a microprocessor, a digital signal processor, and other processors. The memory 1904 and/or the processor 1902 can be virtualized and can be hosted within another computing device of, for example, a cloud network or a data center. The I/O peripherals 1908 include user interfaces, such as a keyboard, screen (e.g., a touch screen), microphone, speaker, other input/output devices, and computing components, such as graphical processing units, serial ports, parallel ports, universal serial buses, and other input/output peripherals. The I/O peripherals 1908 are connected to the processor 1902 through any of the ports coupled to the interface bus 1912. The communication peripherals 1910 are configured to facilitate communication between the computing device 1900 and other computing devices over a communications network and include, for example, a network interface controller, modem, wireless and wired interface cards, antenna, and other communication peripherals.

While the present subject matter has been described in detail with respect to specific embodiments thereof, it will be appreciated that those skilled in the art, upon attaining an understanding of the foregoing may readily produce alterations to, variations of, and equivalents to such embodiments. Accordingly, it should be understood that the present disclosure has been presented for purposes of example rather than limitation, and does not preclude inclusion of such modifications, variations, and/or additions to the present subject matter as would be readily apparent to one of ordinary skill in the art. Indeed, the methods and systems described herein may be embodied in a variety of other forms; furthermore, various omissions, substitutions and changes in the form of the methods and systems described herein may be made without departing from the spirit of the present disclosure. The accompanying claims and their equivalents are intended to cover such forms or modifications as would fall within the scope and spirit of the present disclosure.

Unless specifically stated otherwise, it is appreciated that throughout this specification discussions utilizing terms such as “processing,” “computing,” “calculating,” “determining,” and “identifying” or the like refer to actions or processes of a computing device, such as one or more computers or a similar electronic computing device or devices, that manipulate or transform data represented as physical electronic or magnetic quantities within memories, registers, or other information storage devices, transmission devices, or display devices of the computing platform.

The system or systems discussed herein are not limited to any particular hardware architecture or configuration. A computing device can include any suitable arrangement of components that provide a result conditioned on one or more inputs. Suitable computing devices include multipurpose microprocessor-based computing devices accessing stored software that programs or configures the portable device from a general-purpose computing apparatus to a specialized computing apparatus implementing one or more embodiments of the present subject matter. Any suitable programming, scripting, or other type of language or combinations of languages may be used to implement the teachings contained herein in software to be used in programming or configuring a computing device.

Embodiments of the methods disclosed herein may be performed in the operation of such computing devices. The order of the blocks presented in the examples above can be varied—for example, blocks can be re-ordered, combined, and/or broken into sub-blocks. Certain blocks or processes can be performed in parallel.

Conditional language used herein, such as, among others, “can,” “could,” “might,” “may,” “e.g.,” and the like, unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain examples include, while other examples do not include, certain features, elements, and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more examples or that one or more examples necessarily include logic for deciding, with or without author input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular example.

The terms “comprising,” “including,” “having,” and the like are synonymous and are used inclusively, in an open-ended fashion, and do not exclude additional elements, features, acts, operations, and so forth. Also, the term “or” is used in its inclusive sense (and not in its exclusive sense) so that when used, for example, to connect a list of elements, the term “or” means one, some, or all of the elements in the list. The use of “adapted to” or “configured to” herein is meant as open and inclusive language that does not foreclose devices adapted to or configured to perform additional tasks or steps. Additionally, the use of “based on” is meant to be open and inclusive, in that a process, step, calculation, or other action “based on” one or more recited conditions or values may, in practice, be based on additional conditions or values beyond those recited. Similarly, the use of “based at least in part on” is meant to be open and inclusive, in that a process, step, calculation, or other action “based at least in part on” one or more recited conditions or values may, in practice, be based on additional conditions or values beyond those recited. Headings, lists, and numbering included herein are for ease of explanation only and are not meant to be limiting.

The various features and processes described above may be used independently of one another, or may be combined in various ways. All possible combinations and sub-combinations are intended to fall within the scope of the present disclosure. In addition, certain method or process blocks may be omitted in some implementations. The methods and processes described herein are also not limited to any particular sequence, and the blocks or states relating thereto can be performed in other sequences that are appropriate. For example, described blocks or states may be performed in an order other than that specifically disclosed, or multiple blocks or states may be combined in a single block or state. The example blocks or states may be performed in serial, in parallel, or in some other manner. Blocks or states may be added to or removed from the disclosed examples. Similarly, the example systems and components described herein may be configured differently than described. For example, elements may be added to, removed from, or rearranged compared to the disclosed examples. 

What is claimed is:
 1. A system, comprising: a button; a light source; a microphone; a processor; a power switch coupled to a power line between the microphone and a power source; a data switch coupled to a data line between the microphone and the processor; and a controller coupled with the button, the light source, the power switch, the data switch, and the processor, the controller configured to: receive button ON data from the button, the button ON data indicating a first request to disable the microphone; and based on the button ON data: send, to the power switch, first mute state data, the first mute state data causing the microphone to be decoupled from the power source, send, to the data switch, second mute state data, the second mute state data causing data bits on the data line to have a zero value, send, to the light source, light ON data, the light ON data causing light emission by the light source, and send, to the processor, sensor status data indicating that the microphone is disabled, and wherein the processor is configured to send, to a plurality of voice clients executing on the processor and in response to receiving the sensor status data, first notification data indicating that the microphone is disabled.
 2. The system of claim 1, further comprising: a camera; a second power switch coupled to a second power line between the camera and the power source; and a second data switch coupled to a second data line between the camera and the processor, wherein the controller is further configured to: send the first mute state data to the second power switch, the first mute state data causing the camera to be decoupled from the power source, send the second mute state data to the second data switch, the second mute state data causing the second data switch to send a camera disabled status to the processor, and wherein the processor is further configured to send, to a plurality of video clients executing on the processor and in response to receiving the sensor status data, second notification data indicating that the camera is disabled.
 3. The system of claim 1, wherein the processor is further configured to store the sensor status data in a buffer of the processor, and wherein sending the first notification data comprises: receiving, from a voice client of the plurality of voice clients, a request for a status of the microphone; determining that the microphone is disabled based on the sensor status data stored in the buffer; and sending, in a response to the request for the status, the first notification data to the voice client.
 4. A method implemented on a device, the method comprising: receiving, by a controller of the device, input data indicating a request to disable a sensor of the device; disabling, by the controller based on the input data, the sensor by at least: decoupling the sensor from a power source, and decoupling the sensor from a first data input terminal of a processor of the device, the controller being separate from and coupled with the processor; sending, to a first sensor client that is implemented on the device and configured to receive data corresponding to sensor data generated by the sensor, first output data indicating that the sensor is disabled; sending, to the processor, second output data indicating that the sensor is disabled; and outputting, by a user interface of the device, information indicating that the sensor is disabled.
 5. The method of claim 4, wherein receiving the input data further comprises: receiving the input data based on activation of a physical button of the device; or receiving the input data from the first sensor client.
 6. The method of claim 5, further comprising: disabling, based on the input data, a second sensor of the device by at least: decoupling the second sensor from the power source, and decoupling the second sensor from a second data terminal of the processor; and indicating, to a second sensor client that is implemented on the device and that is associated with the second sensor, that the sensor is disabled.
 7. The method of claim 4 wherein prior to receiving the input data, the method further comprising: receiving, from the first sensor client, first request data and, from a second sensor client implemented on the device, second request data; and generating the input data based on at least one of the first request data or the second request data indicating the request to disable the sensor.
 8. The method of claim 4, further comprising: sending, by the processor, the data corresponding to the sensor data to the first sensor client; receiving, by the controller of the device, the input data; receiving, by the processor from the controller, the second output data indicating that the sensor is disabled; and sending, by the processor to the first sensor client, the first output data, wherein the first output data is sent based on the second output data.
 9. The method of claim 8, the method further comprising: receiving, by the controller, the input data based on activation of a physical button of the device; receiving, by the processor from the controller, third output data, wherein the third output data indicates the activation of the physical button; and receiving, by the processor from the controller, the first output data after a time delay relative to the sending of the third output data.
 10. The method of claim 4, further comprising: receiving, by the processor from a second sensor client implemented on the device, request data indicating a request to disable the sensor, sending, by the processor to the controller of the device, the input data; receiving, by the processor from the controller, sensor status data indicating that the sensor is disabled; and sending, to the first sensor client, the first output data based on the sensor status data.
 11. The method of claim 4, further comprising: receiving second input data indicating a request to enable the sensor; enabling the sensor based on the second input data; receiving, from a light source of the device, an input signal indicating light emission by the light source; disabling the sensor based on the input signal; and sending, to a plurality of sensor clients, third output data indicating that the sensor is disabled.
 12. A device comprising: a button; a user interface; a sensor; a processor; and a controller separate from the processor and coupled with the processor, the controller configured to: receive input data indicating a request to disable the sensor; disable, based on the input data, the sensor by at least: decoupling the sensor from a power source, and decoupling the sensor from a data input terminal of the processor; cause sending, to a first sensor client that is implemented on the device and configured to receive data corresponding to sensor data generated by the sensor, of first output data indicating that the sensor is disabled; cause sending, to the processor, second output data indicating that the sensor is disabled; and cause outputting, by the user interface, of information indicating that the sensor is disabled.
 13. The device of claim 12, further comprising: a first switch coupled to a power line between the sensor and the power source; a second switch coupled to a data line between the sensor and the processor, and wherein the controller is further configured to: receive the input data from the button based on activation of the button; send, to the first switch, third output data causing the decoupling by the first switch of the sensor from the power source by severing a connection of the sensor and the power source via the power line; and send, to the second switch, fourth output data causing the decoupling by the second switch of the sensor from the data input terminal by setting data bits on the data line to have a zero value.
 14. The device of claim 12, wherein the processor is configured to: while the sensor is enabled, receive first request data from the first sensor client and second request data from a second sensor client that is implemented on the device; and generate the input data based on at least one of the first request data or the second request data indicating the request to disable the sensor.
 15. The device of claim 12, further comprising an aggregator configured to: while the sensor is enabled, receive first request data generated by the first sensor client, the first request data received from the first sensor client or from the processor; receive second request data generated by a second sensor client that is implemented on the device; and send, to the controller, the input data based on at least one of the first request data or the second request data indicating the request to disable the sensor.
 16. The device of claim 12, wherein the first output data is notification data, and wherein the processor is configured to: generate the notification data based on the second output data; and send the notification data to the first sensor client.
 17. The device of claim 16, wherein sending the notification data comprises: sending the notification data in a broadcast to a plurality of sensor clients implemented on the device; or storing status data indicating that the sensor has been disabled, and sending the notification data to the first sensor client in a response to a request for a status of the sensor from the first sensor client.
 18. The device of claim 12, wherein the first output data is notification data, and further comprising a distributor configured to: generate the notification data based on the second output data; and send the notification data to the first sensor client or to the processor.
 19. The device of claim 12, wherein the input data is received based on activation of the button of the device, wherein the controller is further configured to: send, to the processor, third output data, wherein the third output data indicates the activation of the button, wherein the second output data is sent after a time delay relative to the sending of the third output data.
 20. The device of claim 12, wherein the controller is further configured to: receive second input data indicating a request to enable the sensor; enable the sensor based on the second input data; receive, from a light source of the device, an input signal indicating light emission by the light source; disable the sensor based on the input signal; and cause sending, to a plurality of sensor clients, of third output data indicating that the sensor is disabled. 